In general, to fix “explicit returns mixed with implicit returns,” every control-flow path in the function should either explicitly return a value or explicitly raise an exception. That means adding a final return (or raise) after conditional logic that might otherwise fall through to the end of the function.

For this specific function, all expected “error” outcomes are already mapped to raise statements in the match result: block, and the happy path has an explicit return. The best way to avoid an implicit return, without changing the intended behavior, is to add a final case _: branch in the match statement that handles any unexpected result value by logging and raising an InternalServerHTTPException. This keeps the external behavior consistent: the endpoint still either returns a CreateProviderResponse or raises an HTTP exception. It also guards against future changes that introduce new result variants without updating this endpoint.

Concretely:

• Edit api/infrastructure/fastapi/endpoints/admin/providers.py.
• Inside create_provider, after the last case InsufficientPermissionError(): block (line 102–103), add a case _: block that logs the unexpected result (optionally) and raises InternalServerHTTPException().
• No new imports are needed, since InternalServerHTTPException and logger are already imported/defined.

In general, to fix “explicit returns mixed with implicit (fall through) returns” you add an explicit return at the end of the function so that no control-flow path can implicitly return None. The explicit return should return a value that is consistent with the function’s annotated return type and with how callers are expected to handle results.

For CreateProviderUseCase.execute, the single best fix is to add a final return statement at the end of the method that returns a value of type CreateProviderUseCaseResult. Since all realistic code paths are already covered by prior returns, this final return will be unreachable in normal execution, serving only as a safety net to satisfy static analysis and future-proof the function against accidental fallthrough. A minimal and non-breaking way is to return a default error type that is already part of the union; given the existing union members, a reasonable choice is ProviderNotReachableError(), which is a generic failure indicating that the provider could not be reached or created. Concretely, in api/use_cases/admin/providers/_createproviderusecase.py, after the final match result: block in execute (after line 126), add a new line with an explicit return ProviderNotReachableError(). No new imports or additional definitions are needed, since ProviderNotReachableError is already imported at the top of the file.